[CI:DOCS] Release notes for v3.2.0-RC2 #10388
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
One of the worst parts of a Podman release is writing the release notes. It requires manually going through all merged commits since the last release, figuring out what was actually done, and writing a small blurb about what was fixed. The worst part of this is the difficulty in finding the commits that were actually included in previous releases - our extensive backports to prior releases mean that there are usually dozens of commits that were included in a prior release, but do not have a matching SHA (as the original author did not do the backport, and often the commit required massaging to cherry-pick in). This script automates the job of finding commits in one release branch that are not in another, with filtering to remove most cherry-picked commits. It makes my life a lot easier during releases, so I figured I'd include it in hack/ so anyone else stuck with the enjoyable task of writing release notes can have a slightly easier life. The script is written in absolutely terrible Ruby and its performance is absolutely terrible, but you only need to run it once per major release and a 30-second wait to generate the list of commits to include isn't bad. Signed-off-by: Matthew Heon <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mheon The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
LGTM |
edsantiago
reviewed
May 18, 2021
There was a problem hiding this comment.
@mheon you must be exhausted. Wow. Impressive job, organizing and summarizing all that.
RELEASE_NOTES.md
Outdated
| - Auto-updating containers can now be done with locally-built images, not just images hosted on a registry, by creating containers with the `io.containers.autoupdate` label set to `local`. | ||
| - Podman now supports the Container Device Interface (CDI) standard. | ||
| - Podman now adds an entry to `/etc/hosts`, `host.containers.internal`, pointing to the current gateway (which, for root containers, is usually a bridge interface on the host system) ([#5651](https://github.com/containers/podman/issues/5651)). | ||
| - The `podman ps`, `podman pos ps`, `podman network list`, `podman secret list`, and `podman volume list` commands now support a `--noheading` option, which will cause Podman to omit the heading line including column names. |
There was a problem hiding this comment.
I suspect you mean **pod** ps, not pos ps?
RELEASE_NOTES.md
Outdated
| - The change in Podman 3.1.2 where the `:z` and `:Z` mount options for volumes were ignored for privileged containers has been reverted after discussion in [#10209](https://github.com/containers/podman/issues/10209). | ||
| - Podman's rootless CNI functionality no longer requires a sidecar container! The removal of the requirement for the `rootless-cni-infra` container means that rootless CNI is not usable on all architectures, not just AMD64, and no longer requires pulling an image ([#8709](https://github.com/containers/podman/issues/8709)). | ||
| - The Image handling code used by Podman has seen a major rewrite to improve code sharing with our other projects, Buildah and CRI-O. We expect this will result in fewer bugs and improved performance in the long term. | ||
| - The `podman auto-update` command now prunes previous versions of images after updating if they are unused, to prevent disk exhaustion after repeated updated ([#10190](https://github.com/containers/podman/issues/10190)). |
There was a problem hiding this comment.
...repeated updates, I think? (not 'updated')?
There was a problem hiding this comment.
Just a guess:
"is not usable on all architectures, not just AMD64" -> "is now usable on all architectures, not just AMD64"
RELEASE_NOTES.md
Outdated
| - The `podman run` and `podman create` commands now support a new option, `--pidfile`. This will create a file when the container is started containing the PID of the first process in the container. | ||
| - The `podman run` and `podman create` commands now support a new option, `--requires`. The `--requires` option adds dependency containers - containers that must be running before the current container. Commands like `podman start` will automatically start the requirements of a container before starting the container itself. | ||
| - Auto-updating containers can now be done with locally-built images, not just images hosted on a registry, by creating containers with the `io.containers.autoupdate` label set to `local`. | ||
| - Podman now supports the Container Device Interface (CDI) standard. |
There was a problem hiding this comment.
Suggested change
| - Podman now supports the Container Device Interface (CDI) standard. | |
| - Podman now supports the [Container Device Interface](https://github.com/container-orchestrated-devices/container-device-interface) (CDI) standard. |
RELEASE_NOTES.md
Outdated
|
|
||
| ### Changes | ||
| - The change in Podman 3.1.2 where the `:z` and `:Z` mount options for volumes were ignored for privileged containers has been reverted after discussion in [#10209](https://github.com/containers/podman/issues/10209). | ||
| - Podman's rootless CNI functionality no longer requires a sidecar container! The removal of the requirement for the `rootless-cni-infra` container means that rootless CNI is not usable on all architectures, not just AMD64, and no longer requires pulling an image ([#8709](https://github.com/containers/podman/issues/8709)). |
There was a problem hiding this comment.
I think you meant "now", not "not"
Suggested change
| - Podman's rootless CNI functionality no longer requires a sidecar container! The removal of the requirement for the `rootless-cni-infra` container means that rootless CNI is not usable on all architectures, not just AMD64, and no longer requires pulling an image ([#8709](https://github.com/containers/podman/issues/8709)). | |
| - Podman's rootless CNI functionality no longer requires a sidecar container! The removal of the requirement for the `rootless-cni-infra` container means that rootless CNI is now usable on all architectures, not just AMD64, and no longer requires pulling an image ([#8709](https://github.com/containers/podman/issues/8709)). |
RELEASE_NOTES.md
Outdated
| ### Changes | ||
| - The change in Podman 3.1.2 where the `:z` and `:Z` mount options for volumes were ignored for privileged containers has been reverted after discussion in [#10209](https://github.com/containers/podman/issues/10209). | ||
| - Podman's rootless CNI functionality no longer requires a sidecar container! The removal of the requirement for the `rootless-cni-infra` container means that rootless CNI is not usable on all architectures, not just AMD64, and no longer requires pulling an image ([#8709](https://github.com/containers/podman/issues/8709)). | ||
| - The Image handling code used by Podman has seen a major rewrite to improve code sharing with our other projects, Buildah and CRI-O. We expect this will result in fewer bugs and improved performance in the long term. |
There was a problem hiding this comment.
Suggest:
Suggested change
| - The Image handling code used by Podman has seen a major rewrite to improve code sharing with our other projects, Buildah and CRI-O. We expect this will result in fewer bugs and improved performance in the long term. | |
| - The Image handling code used by Podman has seen a major rewrite to improve code sharing with our other projects, Buildah and CRI-O. This should result in fewer bugs, it has improved performance slightly already, and we expect further performance gains and easier maintenance in the long term as work is ongoing. |
| - The `podman play kube` now treats environment variables configured as references to a `ConfigMap` as mandatory unless the `optional` parameter was set; this better matches the behavior of Kubernetes. | ||
| - Podman now supports the `--context=default` flag from Docker as a no-op for compatibility purposes. | ||
| - When Podman is run as root, but without `CAP_SYS_ADMIN` being available, it will run in a user namespace using the same code as rootless Podman (instead of failing outright). | ||
| - The `podman info` command now includes the path of the Seccomp profile Podman is using, and whether Podman is connected to a remote service or running containers locally. |
There was a problem hiding this comment.
Suggested change
| - The `podman info` command now includes the path of the Seccomp profile Podman is using, and whether Podman is connected to a remote service or running containers locally. | |
| - The `podman info` command now includes the path of the seccomp profile Podman is using and whether Podman is connected to a remote service or running containers locally. |
RELEASE_NOTES.md
Outdated
| - Podman now supports the `--context=default` flag from Docker as a no-op for compatibility purposes. | ||
| - When Podman is run as root, but without `CAP_SYS_ADMIN` being available, it will run in a user namespace using the same code as rootless Podman (instead of failing outright). | ||
| - The `podman info` command now includes the path of the Seccomp profile Podman is using, and whether Podman is connected to a remote service or running containers locally. | ||
| - Containers created with the `--rm` option now automatically use the `volatile` storage flag when available for their root filesystems, causing them to not write changes to disk as often as they will be removed at completion anyways. This should result in improved performance. |
There was a problem hiding this comment.
Suggested change
| - Containers created with the `--rm` option now automatically use the `volatile` storage flag when available for their root filesystems, causing them to not write changes to disk as often as they will be removed at completion anyways. This should result in improved performance. | |
| - Containers created with the `--rm` option now automatically use the `volatile` storage flag when available for their root filesystems, causing them not to write changes to disk as often as they will be removed at completion anyways. This should result in improved performance. |
Luap99
reviewed
May 19, 2021
RELEASE_NOTES.md
Outdated
| - When Podman is run as root, but without `CAP_SYS_ADMIN` being available, it will run in a user namespace using the same code as rootless Podman (instead of failing outright). | ||
| - The `podman info` command now includes the path of the Seccomp profile Podman is using, and whether Podman is connected to a remote service or running containers locally. | ||
| - Containers created with the `--rm` option now automatically use the `volatile` storage flag when available for their root filesystems, causing them to not write changes to disk as often as they will be removed at completion anyways. This should result in improved performance. | ||
| - The `podman generate systemd` command will now include environment variables referenced by the container in generated unit files if the value would be looked up from the system environment. |
There was a problem hiding this comment.
Suggested change
| - The `podman generate systemd` command will now include environment variables referenced by the container in generated unit files if the value would be looked up from the system environment. | |
| - The `podman generate systemd --new` command will now include environment variables referenced by the container in generated unit files if the value would be looked up from the system environment. |
Missing the updated vendor bits, but the vendor dance is not yet done. Signed-off-by: Matthew Heon <[email protected]>
mheon
force-pushed
the
release_notes_320rc2
branch
from
30b8d6e to
38ec00c
Compare
|
Update pushed, comments addressed |
|
/lgtm |
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Should be complete aside from the vendor-dance "Updated Buildah to ..." bits, which aren't ready yet because we're still vendoring.
I cherry-picked in my release branch commit-identifier script because I used it to make these.